home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_2
/
sfsfcom.zip
/
SFSF.TXT
< prev
next >
Wrap
Text File
|
1990-09-23
|
15KB
|
449 lines
-------------------------------------------------------------------------------------
SFSFCOM V3 from Bob Zimmerman
-------------------------------------------------------------------------------------
( A history of versions changes are in the back of this
doc! )
If you ever need to create a file for a "one time download"
for a user, and then you delete it from the system, SFSFCOM
is for you!
SFSFCOM was created to supplement Spitfire's File Menu.
There are times I would like to make a file available to a
user for downloading. I only want one or two people to be
able to download it.
After they download their files, I want the files to
automatically be deleted.
I sell software. If you register some of my software, I will
create a special copy of it for you. I would like ONLY YOU
to be able to download the file. When you have, I would like
to delete it to regain disk space.
SFSFCOM does all of this automatically.
- Page 1 -
-------------------------------------------------------------------------------------
SFSFCOM V3 from Bob Zimmerman
-------------------------------------------------------------------------------------
Installation:
-------------
Step 1 Create a directory for SFSFCOM. For the sake of
example, let us say that we create a directory
called D:\SFSFCOM.
Step 2 UNZIP file SFSFCOM.ZIP into your new directory.
The file SFSFCOM is the door program. The SFSFADD
is a utility program. SFSF.DAT will automatically
be created for you, if it does not already exist.
Step 3 You may install SFSFCOM on the doors menu, from
Wildfire, from the SFMNUEXT menu, or from the
Sysop Configurable. I will discuss installing it
from the Sysop Configurable (option K) of the File
Menu.
To install on the File Menu as option "K":
------------------------------------------
Create SFFILE.BAT in your Spitfire Directory
(as the Spitfire manual explains). The
SFFILE.BAT should contain:
COPY SFFILE.DAT D:\SFSFCOM
D:
CD\SFSFCOM
SFSFCOM /CALLER
To install from a door:
-----------------------
Modify SF.BAT to include the following
statements after the appropriate door
"label".
COPY SFDOORS.DAT D:\SFSFCOM
D:
CD\SFSFCOM
SFSFCOM /CALLER
Step 4 That's it. The /CALLER parm says to "log" any
downloads in the CALLERS.LOG file (same as
Spitfire does). If you leave off /CALLER, it will
write the data to a file called SFSF.LOG.
- Page 2 -
-------------------------------------------------------------------------------------
SFSFCOM V3 from Bob Zimmerman
-------------------------------------------------------------------------------------
There are now 3 other parameters that may follow
SFSFCOM. First is the word /NOLOG which eliminates
the logging completely.
Next, /NOBATCH specifies you are running with a
version of DSZ previous to 4/6/1988 (which is when
the Zmodem batch support was added to DSZ).
Finally, /Wfile.ext specifies the location and
name of a work file used when performing batch
transfers. This file is about 100 bytes (that is
right - extremely small) and is only created when
doing batch transfers. The default is
C:\FILES.$$$. If you do specify a file name, you
MUST specify the Drive, followed by a colon,
followed by a backslash, followed by the full path
and file name. You must specify the WHOLE thing.
Step 5 You must run SFSFADD from the SFSFCOM directory.
In other words, you should go to the D:\SFSFCOM
directory first (using the CD command) and then
begin SFSFADD.
Every time you want to "allow" a user to download
a file, you simply run SFSFADD. This program will
prompt you for the User Name, the File Name,
whether the file should be deleted after it is
downloaded, and a comment about the file.
THE FILE CAN BE ANYWHERE ON DISK - PREFERABLY NOT
IN THE SPITFIRE FILE AREAS! This will prevent
anyone but the authorized user from downloading
it.
When running SFSFADD, you may use the "?" in the
User Name and File Name to get help. I RECOMMEND
YOU TRY BOTH OF THESE FEATURES AT LEAST ONCE!
Step 6 Make sure DSZ is installed anywhere in your PATH!
Step 7 In your AUTOEXEC.BAT, add the line SET
SFPATH=C:\SF where C:\SF is the path containing
Spitfire.Exe.
- Page 3 -
-------------------------------------------------------------------------------------
SFSFCOM V3 from Bob Zimmerman
-------------------------------------------------------------------------------------
Registration
------------
All questions should be directed to:
Bob Zimmerman
Sysop - The Mainframe BBS
708-364-0425
9600/2400/1200/0300
The Mainframe
PO Box 1387
Arlington Heights, IL
60006
MCI Mail:
R. Zimmerman 386-4706
Compuserv 72371,1700
The above mailing address should be used for the
registration fee. For the current version (1.0),
registration is $18.00. When this is received, a ZIP file
will be created on my BBS and made available for you to
download. If you want me to send you the disk and this
manual printed, add $5 for 5 1/4 disk or $7 for 3 1/2 disk.
If you prefer, your package can be delivered via EASYPLEX of
Compuserv. Registration plus Easyplex delivery will cost an
additional $5.
Registration will get you a specially compiled version that
eliminates the front "unregistered copy" message and will
also get you full technical support and free upgrades until
a major revision (at least 3 updates free).
You are granted 30 days to evaluate this program. After that
30 day period, if you choose to continue running this
program, you must register the product!
- Page 4 -
-------------------------------------------------------------------------------------
SFSFCOM V3 from Bob Zimmerman
-------------------------------------------------------------------------------------
Revision History
----------------
Version 1.1 Fixed the program so it will work with
SFMAIN.DAT, SFFILE.DAT SFMESS.DAT or
SFDOORS.DAT. You were having to copy whatever
file Spitfire made to SFDOORS.DAT. Now you
don't have to anymore.
Version 1.5 Yep - it jumped to 1.5. I have cleaned up a
great deal performance wise and added some
code that will check if the DSZ transfer
completed ok. It no longer asks the user did
he receive it ok... It simply checks DSZ
return code. If it is equal to 0 (transfer
worked), then it will delete teh SFSF.DAT
record and if requested by SFSFADD, delete
the file that was transfered.
SFSFADD has a new feature as well. It will
automatically add a record to the message
file telling the user there is a file
waiting. You must specify the text of the
message...
Version 1.6 If you installed this utility without DSZ in
your path, then it would not run and if you
had any files for deletion, they were deleted
after the user downloaded them.
Now, a message is displayed on the console
telling you the file DSZ.COM could not be
found (in the current SFSFCOM directory or
anywhere in the path).
ALSO - MAJOR ADDITION TO SFSFADD and all my
future programs... Use the
SET SFPATH=spitfire path
in your autoexec.bat file. This will tell all
my utils where to find Spitfire.Exe and all
of the user files etc...
When you run SFSFADD to add a record, it will
first search for a command line parameter
/PC:\SF where C:\SF is the spitfire path, if
that is not found, it searches for a previous
SET command (e.g. SET SFPATH=C:\SF), and
finally, if all else fails, it prompts you
for "where is the path?")...
- Page 5 -
-------------------------------------------------------------------------------------
SFSFCOM V3 from Bob Zimmerman
-------------------------------------------------------------------------------------
This suggestion comes from Diana Lucas and is
greatly appreciated!
Version 1.7 SFSFCOM now supports batch downloads. If the
user tries downloading using Zmodem or Ymodem
batch, and he has more then one file waiting,
he will be given the option of downloading
all the files in a "batch" at one time.
If at any time any of the files fail to
download, the whole batch is considered "NOT
DOWNLOADED" and the files remain in the users
queue. He may use option 2 to remove the
files he has successfully received.
Version 1.8 This version only modifies this
documentation. Someone brought to my
attention that the installation instructions
really "sucked". Well, when I blow it, I do
it well (or lousy depending on your
perspective).
V1.8 basically has the installation
instructions redone. They may be found in
this doc. The program itself has not been
changed.
Version 1.9 SFSFADD has been update to work with Spitfire
2.8 and on. This is the only change. It will
not work with previous versions of Spitfire.
It will add the message to a user in Message
Conference #1 only.
If you have a default message you would like
to send the user, you may use an environment
variable of
SET SFSFADD = <whatever message you want>
Be careful, as your environment space may be
running out and this could cause problems
with Zmodem execution etc...
Version 1.91 the keyword /UPDATE_DL will have SFSFCOM
update the callers statistics...
- Page 6 -
-------------------------------------------------------------------------------------
SFSFCOM V3 from Bob Zimmerman
-------------------------------------------------------------------------------------
Version 3.0 Updated the source for Spitfire 3.0. No
longer requires the SFSYSDAT file, and
supports file locking and sharing.
When building a batch download, the DSZ
internal file for batch downloads now has the
node number appended to it so that multiple
nodes can run this door at the same time.
- Page 7 -